pp108 : Using Custom Templates

Using Custom Templates
This topic describes the procedure to use the custom templates created while deploying applications.

While deploying applications, you can choose to save a set of applications to be deployed as a template. These templates can be used to deploy applications in the same computer or other computer too. You can deploy the custom template on another computer through command-line as described in the second point below:

You cannot create custom templates for packages being deployed in the Organization space.
  • To deploy applications in a custom template on the same instance, do the following:
    1. On CUSP > My Applications, click (Application Deployer). A Deployment Overview page appears, displaying the templates under the Custom Templates head.
    2. Select the relevant template, right-click on the template and click 'Express Deploy'. The applications which are part of the template are deployed.
  • To deploy applications in a custom template on another instance, do the following:
    1. Open the instance where you saved the templates.
    2. On CUSP > My Applications, click (Application Deployer). A Deployment Overview page appears, displaying the templates under the Custom Templates head.
    3. Right-click the relevant template, click View. A Template View window appears, displaying the XML of the template.
    4. Copy the XML to a file on the computer to be deployed (For example: test.xml). The template is created and you can use this as an input file for your command-line deployment.
    5. If required, you can create a userInput file and save it to a location on the computer to be deployed.
      This step is needed if you have to provide additional inputs for your applications in the template while deploying. For example, if your application contains MDM content, then you may need to provide a different database details. In that case, you must create the user input file with all the relevant database details.
      You can refer to the CAPUserInput file in the captemplates folder of the Process Platform zip folder as a reference.
    6. Ensure that the relevant applications in the template are present in the <Process_Platform_Installation_Directory>/capcontent/packages folder.
    7. From the extracted zip folder, open the cap-silent-install.properties file in a text editor. Modify the following properties according to the configuration of the computer.
      • cordys.cap.silent.template.inputfile refers to the file path which contains template of the required applications to be deployed.
      • cordys.cap.silent.userinputfile refers to the file path which contains user inputs for the applications.
      • cordys.cap.silent.deployment.server refers to the name of the computer on which Process Platform baseline installation is done.
      • cordys.cap.silent.deployment.port refers to the port number of the website on which Process Platform baseline installation is done.
      • cordys.cap.silent.deployment.failOnError decides whether to stop or continue the execution of applications if one of them has failed to deploy or upgrade. This is an optional property and the default value is false.
    8. Set environment variable CORDYS_HOME pointing to the Process Platform installation directory.
    9. Set PATH=%PATH%;%CORDYS_HOME%/lib .
    10. Set CLASSPATH=%CLASSPATH%;%CORDYS_HOME%/cordyscp.jar.
    11. Run the following java command:

      java -Duser.name=<ldapuser> -cp <Process_Platform_Installation_Directory>\cordyscp.jar com.cordys.cap.tool.silentdeployment.SilentCAPDeployer <Location of cap-silent-install.properties file>

where ldapuser is the user created during the Process Platform baseline deployment.

The applications will be deployed using custom template. The status of each application is displayed in the command prompt as it is being deployed.